That's odd, the tests pass locally.

Edit: Likely a fluke due to timer resolution. Maybe using FRAMEBUDGET * 2 in the throttle tests would make them more reliable?

I removed the build artefact from the branch the patch is based on.

Note that, when running npm run build, I ended up with this line

looking like this:

        }, function(path, params) {
            router.setPath(defaultRoute, null, {replace: true})
        })

I had to fix it manually.

This works in practice (the original problem case jsbin visibly just works), but not in theory — I couldn't get any lifecycle tests to pass this. I guess I'll have to invoke the autoredraw API…